Method and apparatus for communication of terminal in mobile communication system

ABSTRACT

The disclosure relates to a communication technique and a system thereof for fusing, with IoT technology, a 5G communication system for supporting a higher data transmission rate than a 4G system. The disclosure may be applied to intelligent services (such as smart homes, smart buildings, smart cities, smart cars or connected cars, health care, digital education, retail business, and security and safety related services, etc.) on the basis of 5G communication technology and IoT related technology. The disclosure may provide a method for setting the monitoring of an application server (AS), the method comprising the steps of: transmitting, to a service capability exposure function (SCEF), a first message which comprises information on an identifier, which indicates a group including a plurality of terminals, and a waiting time and instructs to report monitoring information on the group including a plurality of terminals; and receiving, from the SCEF, a second message comprising the monitoring information on the group of a plurality of terminals.

TECHNICAL FIELD

An embodiment of the present invention relates to a method and apparatusfor communication of a terminal in a mobile communication system. Inaddition, an embodiment of the present invention relates to a method andapparatus for group terminal management. In addition, an embodiment ofthe present invention relates to a method and apparatus for efficientlycontrolling a plurality of terminals. In addition, an embodiment of thepresent invention relates to a method and apparatus for communicationvia a path suitable for a service characteristic. In addition, anembodiment of the present invention relates to a method and apparatusfor communication of service contents distributed near a user. Inaddition, an embodiment of the present invention relates to a method andapparatus for transmitting and receiving data at a terminal connected toa plurality of third-party servers. In addition, an embodiment of thepresent invention relates to a method and apparatus for managing abearer when a cellular Internet of things (IoT) terminal uses atelephone service.

BACKGROUND ART

To meet the demand for wireless data traffic having increased sincedeployment of 4th generation (4G) communication systems, efforts havebeen made to develop an improved 5th generation (5G or pre-5G)communication system. Therefore, the 5G or pre-5G communication systemis also called a ‘Beyond 4G Network’ or a ‘Post long term evolution(LTE) System’. The 5G communication system is considered to beimplemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, soas to accomplish higher data rates. To decrease the propagation loss ofradio waves and increase the transmission distance, various techniquessuch as beamforming, massive multiple-input multiple-output (massiveMIMO), full dimensional MIMO (FD-MIMO), an array antenna, analogbeamforming, and a large scale antenna are discussed in the 5Gcommunication system. Also, in the 5G communication system, thedevelopment for system network improvement is underway based on anadvanced small cell, a cloud radio access network (cloud RAN), anultra-dense network, device-to-device (D2D) communication, wirelessbackhaul, a moving network, cooperative communication, coordinatedmulti-points (CoMP), reception-end interference cancellation, and thelike. Further, in the 5G system, hybrid frequency shift keying (FSK) andquadrature amplitude modulation (QAM) (FQAM) and sliding windowsuperposition coding (SWSC) have been developed as advanced codingmodulation (ACM) schemes, and filter bank multi carrier (FBMC),non-orthogonal multiple access (NOMA), and sparse code multiple access(SCMA) have been developed as advanced access technologies.

Meanwhile, the Internet, which is a human centered connectivity networkwhere humans generate and consume information, is now evolving to theInternet of things (IoT) where distributed entities, such as things,exchange and process information without human intervention. Further,the Internet of everything (IoE), which is a combination of IoTtechnology and big data processing technology through connection with acloud server, has emerged. As technology elements, such as sensingtechnology, wired/wireless communication and network infrastructure,service interface technology, and security technology, have beendemanded for IoT implementation, a sensor network, machine-to-machine(M2M) communication, machine type communication (MTC), and so forth havebeen recently researched. Such an IoT environment may provideintelligent Internet technology services that create a new value tohuman life by collecting and analyzing data generated among connectedthings. The IoT may be applied to a variety of fields including smarthome, smart building, smart city, smart car or connected car, smartgrid, health care, smart appliances, advanced medical service, etc.through convergence and combination between existing informationtechnology (IT) and various industrial applications.

In line with this, various attempts have been made to apply the 5Gcommunication system to the IoT network. For example, technologies suchas a sensor network, machine type communication (MTC), andmachine-to-machine (M2M) communication are being implemented on thebasis of 5G communication technologies such as beamforming, MIMO, and anarray antenna. The use of a cloud radio access network (cloud RAN) forbig data processing technology is one example of convergence between the5G technology and the IoT technology.

The IoT technology is in the spotlight in various fields, andcommunication operators and vendors are developing various applicationsand systems using IoT. Among various IoT solutions, the cellular IoT(hereinafter referred to as ‘CIoT’) which utilizes a licensed frequencyband allocated to the cellular system has lately attracted attention.This is because the cellular system can provide relatively reliablecommunication as compared to the non-cellular system and thus canprovide a stable service. In connection with the CIoT, standardizationactivities such as evolved machine type communication (eMTC) and globalsystem for mobile communications enhanced data rates for global systemfor mobile communication (GSM) enhanced data rates for GSM (EDGE) radioaccess network (GERAN) CIoT are actively underway, and needs ofcommunication operators often have a decisive influence on standarddecisions due to the nature of standardization activities.

Advanced communication technology enables communication between allthings as well as between users, and therefore this is called IoT. Forexample, a user can have various types of electronic devices, and all ofthese electronic devices can be connected to each other through mobilecommunication, short-range communication, various sensors, etc. toprovide more convenient functions to the user while allowing anefficient inter-device control. These electronic devices may be referredto as IoT devices or IoT terminals. Another example of IoT devices ismeasuring equipment that measures the electricity usage, water usage,etc. of a building and delivers a measurement value over the network. Asstill another example, IoT devices for public safety may be installed inpublic or remote places to monitor safety situations, and these devicesmay notify an event status through the network when a certain eventoccurs. As yet another example, home appliances may have a networkaccess function and thereby report its state or perform a specificoperation in response to a device trigger command from a user.

The IoT device includes a mobile communication module such as LTE or ashort-range communication module such as Bluetooth, WiFi, Zigbee, ornear-field communication (NFC).

An LTE terminal may operate at the LTE carrier frequency, and mayoperate in the industrial, scientific, and medical (ISM) band.

DISCLOSURE OF INVENTION Technical Problem

It is an object of the present invention to provide a method andapparatus for an enhanced mobile communication service.

Solution to Problem

According to an embodiment of the present invention, a monitoringconfiguration method of an application server (AS) may comprise steps oftransmitting, to a service capability exposure function (SCEF), a firstmessage including an identifier indicating a group including a pluralityof terminals and information on a wait time and information indicatingto report monitoring information for the group; and receiving, from theSCEF, a second message including the monitoring information for thegroup.

In addition, according to an embodiment of the present invention, an ASmay comprise a transceiver transmitting and receiving signals; and acontroller controlling to transmit, to SCEF, a first message includingan identifier indicating a group including a plurality of terminals andinformation on a wait time and instructs to report monitoringinformation for the group, and controlling to receive, from the SCEF, asecond message including the monitoring information for the group.

In addition, according to an embodiment of the present invention, amonitoring configuration method of a SCEF may comprise steps ofreceiving, from an AS, a first message including a group identifierindicating a group of a plurality of terminals and information on a waittime and information indicating to report monitoring information for thegroup; transmitting, to a home subscriber server (HSS), a second messageincluding an identifier identifying connection between the SCEF and theHSS, the group identifier, and the information on the wait time;receiving a third message including the monitoring information for thegroup from the HSS; and transmitting a fourth message including themonitoring information for the group to the AS.

In addition, according to an embodiment of the present invention, a SCEFmay comprise a transceiver transmitting and receiving signals; and acontroller controlling to receive, from an AS, a first message includinga group identifier indicating a group of a plurality of terminals andinformation on a wait time and instructs to report monitoringinformation for the group, controlling to transmit, to a HSS, a secondmessage including an identifier identifying connection between the SCEFand the HSS, the group identifier, and the information on the wait time,controlling to receive a third message including the monitoringinformation for the group from the HSS, and controlling to transmit afourth message including the monitoring information for the group to theAS.

In addition, according to an embodiment of the present invention, amonitoring configuration method of an HSS may comprise steps ofreceiving, from a SCEF, a first message including an identifieridentifying connection between the HSS and the SCEF, a group identifierindicating a group of a plurality of terminals, and information about await time; transmitting a second message configuring a monitoring typeto an entity of managing mobility of the plurality of terminals;receiving a third message including monitoring information correspondingto the monitoring type from the entity of managing mobility; andtransmitting a fourth message including the monitoring information tothe SCEF.

In addition, according to an embodiment of the present invention, an HSSmay comprise a transceiver transmitting and receiving signals; and acontroller controlling to receive, from a SCEF, a first messageincluding an identifier identifying connection between the HSS and theSCEF, a group identifier indicating a group of a plurality of terminals,and information on a wait time, controlling to transmit a second messageconfiguring a monitoring type to an entity of managing mobility of theplurality of terminals, controlling to receive a third message includingmonitoring information corresponding to the monitoring type from theentity of managing mobility, and controlling to transmit a fourthmessage including the monitoring information to the SCEF.

Technical problems and solutions of the present invention are notlimited to those mentioned above. Even though not mentioned above, othertechnical problems and solutions will be apparent to those skilled inthe art from the description below.

Advantageous Effects of Invention

According to an embodiment of the present invention, it is possible toprovide a method and apparatus for group terminal management. Inaddition, according to an embodiment of the present invention, it ispossible to provide a method and apparatus for efficiently controlling aplurality of terminals. In addition, according to an embodiment of thepresent invention, it is possible to provide a method and apparatus forcommunication via a path suitable for a service characteristic.

In addition, according to an embodiment of the present invention, it ispossible to provide a method and apparatus for communication of servicecontents distributed near a user. In addition, according to anembodiment of the present invention, it is possible to provide a methodand apparatus for transmitting and receiving data at a terminalconnected to a plurality of third-party servers. Further, according toan embodiment of the present invention, it is possible to provide amethod and apparatus for managing a bearer when a cellular Internet ofthings (CIoT) terminal uses a telephone service.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating a procedure between an servicescapability server (SCS)/application server (AS), a service capabilityexposure function (SCEF), a home subscriber server (HSS), and a mobilitymanagement entity (MME)/serving general packet radio service (GPRS)support node (SGSN) (MME/SGSN) in order to create a group for managing aterminal in an embodiment of the present invention.

FIG. 2 is a diagram illustrating a monitoring event configurationprocedure according to a second embodiment of the present invention.

FIG. 3 is a diagram illustrating a monitoring event reporting procedurein an embodiment of the present invention.

FIG. 4 is a diagram illustrating a communication pattern parameterprovisioning procedure according to an embodiment of the presentinvention.

FIG. 5 is a diagram illustrating a structure of a communication systemfor a terminal or a machine type communication (MTC) apparatus accordingto an embodiment of the present invention.

FIG. 6 is a diagram illustrating architecture for service capabilityexposure according to an embodiment of the present invention.

FIG. 7 is a diagram illustrating roaming architecture for servicecapability exposure according to an embodiment of the present invention.

FIG. 8 is a diagram illustrating a group message delivery procedureusing multimedia broadcast/multicast services (MBMS) according to anembodiment of the present invention.

FIG. 9 is a diagram illustrating architecture of a radio access networkand a core network according to an embodiment of the present invention.

FIG. 10 is a diagram illustrating architecture of a radio access networkand a core network according to another embodiment of the presentinvention.

FIG. 11 is a diagram illustrating architecture of a radio access networkand a core network according to still another embodiment of the presentinvention.

FIG. 12 is a diagram illustrating architecture of a radio access networkand a core network according to yet another embodiment of the presentinvention.

FIG. 13 is a diagram illustrating a scheme of activating contentdelivery network (CDN) by using SCEF.

FIG. 14 is a diagram illustrating a configuration procedure forestablishing a data connection between an SCS/AS, an SCEF, and an MME inan embodiment of the present invention.

FIG. 15 is a diagram illustrating a method for utilizing an evolvedpacket system (EPS) bearer identification (ID) at a terminal and an MMEin an embodiment of the present invention.

FIG. 16 is a diagram illustrating a method for utilizing a referenceidentifier of an SCEF or an identifier of an SCS/AS at a terminal in anembodiment of the present invention.

FIG. 17 is a diagram illustrating an MO-based bearer management methodin an embodiment of the present invention.

FIG. 18 is a diagram illustrating an MT-based bearer management methodin an embodiment of the present invention.

FIG. 19 is a diagram illustrating a procedure after a call is terminatedin an embodiment of the present invention.

FIG. 20 is a diagram illustrating an AS according to an embodiment ofthe present invention.

FIG. 21 is a diagram illustrating an SCEF according to an embodiment ofthe present invention.

FIG. 22 is a diagram illustrating an HSS according to an embodiment ofthe present invention.

MODE FOR THE INVENTION

Hereinafter, embodiments of the present invention will be described withreference to the accompanying drawings.

In the following description of embodiments, descriptions of techniquesthat are well known in the art and not directly related to the presentinvention are omitted. This is to clearly convey the subject matter ofthe present invention by omitting any unnecessary explanation.

For the same reason, some elements in the drawings are exaggerated,omitted, or schematically illustrated. Also, the size of each elementdoes not entirely reflect the actual size. In the drawings, the same orcorresponding elements are denoted by the same reference numerals.

The advantages and features of the present invention and the manner ofachieving them will become apparent with reference to the embodimentsdescribed in detail below and with reference to the accompanyingdrawings. The present invention may, however, be embodied in manydifferent forms and should not be construed as being limited to theembodiments set forth herein. Rather, these embodiments are provided sothat this invention will be thorough and complete and will fully conveythe scope of the invention to those skilled in the art. To fullydisclose the scope of the invention to those skilled in the art, theinvention is only defined by the scope of claims.

It will be understood that each block of the flowchart illustrations,and combinations of blocks in the flowchart illustrations, may beimplemented by computer program instructions. These computer programinstructions may be provided to a processor of a general purposecomputer, special purpose computer, or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which are executed via the processor of the computer or otherprogrammable data processing apparatus, generate means for implementingthe functions specified in the flowchart block or blocks. These computerprogram instructions may also be stored in a computer usable orcomputer-readable memory that may direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer usable orcomputer-readable memory produce an article of manufacture includinginstruction means that implement the function specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto a computer or other programmable data processing apparatus to causea series of operational steps to be performed on the computer or otherprogrammable apparatus to produce a computer implemented process suchthat the instructions that are executed on the computer or otherprogrammable apparatus provide steps for implementing the functionsspecified in the flowchart block or blocks.

In addition, each block of the flowchart illustrations may represent amodule, segment, or portion of code, which comprises one or moreexecutable instructions for implementing the specified logicalfunction(s). It should also be noted that in some alternativeimplementations, the functions noted in the blocks may occur out of theorder. For example, two blocks shown in succession may in fact beexecuted substantially concurrently or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved.

The term “unit”, as used herein, may refer to a software or hardwarecomponent or device, such as a field programmable gate array (FPGA) orapplication specific integrated circuit (ASIC), which performs certaintasks. A unit may be configured to reside on an addressable storagemedium and configured to execute on one or more processors. Thus, amodule or unit may include, by way of example, components, such assoftware components, object-oriented software components, classcomponents and task components, processes, functions, attributes,procedures, subroutines, segments of program code, drivers, firmware,microcode, circuitry, data, databases, data structures, tables, arrays,and variables. The functionality provided for in the components andunits may be combined into fewer components and units or furtherseparated into additional components and modules. In addition, thecomponents and units may be implemented to operate one or more centralprocessing units (CPUs) in a device or a secure multimedia card.

Although embodiments of the present invention will be describedhereinafter by mainly targeting long-term evolution (LTE) and evolvedpacket core (EPC), which are a radio access network (RAN) and a corenetwork (CN) defined as standards by the 3rd generation partnershipproject (3GPP), the essential concept of the present invention may bealso applied to any other communication system having a similartechnical background without departing from the scope of this inventionas will be apparent to those skilled in the art.

For convenience of explanation, some terms and names defined instandards of the 3rd generation partnership project long term evolution(3GPP LTE) may be used. However, the present invention is not limited bysuch terms and names, and can be equally applied to systems conformingto other standards.

An LTE terminal and an Internet of things (IoT) terminal to be usedhereinafter refer to a mobile terminal, also referred to as userequipment (UE), capable of wireless communication. For example, the LTEterminal and the IoT terminal may be a personal digital assistant (PDA),a smart phone, a mobile phone, a tablet computer, a notebook, or thelike which includes a communication function. In addition, the LTEterminal and the IoT terminal may be a measuring device for checkingwater usage, electricity usage, or temperature, an alarm device, such asa fire alarm or an earthquake alarm, for recognizing and reporting aspecific situation, or home appliances, such as an air conditioner, arefrigerator, an air purifier, a boiler, or a vacuum cleaner, having acommunication function. All things capable of communication as well asthe above-mentioned types will be referred to as the IoT terminals inthe present invention. Among the IoT terminals, a terminal using thecellular network will be referred to as a cellular Internet of things(CIoT) terminal. The CIoT terminal may refer to a terminal thattransmits a small amount of data in the LTE network. In the presentinvention, an apparatus, function, and operation for a CIoT serviceinclude an apparatus, function, and operation for small datatransmission in the LTE network. IoT data may refer to data sent by theIoT terminal or a small amount of data sent by any type of terminal.

First Embodiment

A first embodiment of the present invention relates to a method forcreating and managing a group of terminals and to an apparatus forperforming the method.

In the first embodiment, a services capability server (SCS)/applicationserver (AS) refers to a 3rd party application server. A servicecapability exposure function (SCEF) performs a function of connectingthe SCS/AS to an evolved packet system (EPS) network and is located in atrusted domain. The SCEF is connected to a home subscriber server (HSS)and receives information about terminals (UEs). The SCEF is connected toa mobility management entity (MME) via the HSS and can exchangeinformation. There are a UE-MME connection, an MME-SCEF connection andan SCEF-SCS/AS connection, and information about UEs may be exchangedthrough these connections.

The first embodiment of the present invention proposes a method and anapparatus for creating a group for management of several UEs andmanaging this group.

The HSS may support a group management request. If the HSS does notsupport the group management request, the group management request sentby the SCS/AS is rejected by the HSS or by the SCEF which knows that theHSS does not support the group management request.

Even if the HSS supports the group management request, the followingcases may occur. A certain relevant CN node may perform group-basedmonitoring/communication pattern provisioning and group-specific NAS(non-access stratum) level congestion control, and other relevant CNnode may not perform at least one of group-basedmonitoring/communication pattern provisioning and group-specific NAS(non-access stratum) level congestion control.

FIG. 1 is a diagram illustrating a procedure between an SCS/AS, an SCEF,an HSS, and a mobility management entity (MME)/serving general packetradio service (GPRS) support node (SGSN) (MME/SGSN) in order to create agroup for managing a terminal (i.e., UE) in an embodiment of the presentinvention.

Referring to FIG. 1, a wireless communication system may include anMME/SGSN 105, an interworking SCEF (IWK-SCEF) 110, an HSS 115, an SCEF120, and an SCS/AS 125.

At operation 151, the SCS/AS 125 sends a group management requestmessage to the SCEF 120. This message includes at least one of an SCS/ASidentifier (ID), an SCS/AS reference ID for identifying a connectionbetween the SCS/AS and the SCEF, a group management type, and anexternal group ID for indicating the ID of an external group to whichthe UE belongs. The group management type may include groupcreation/modification/removal. The external group ID may be associatedwith an external ID for identifying the UE or a mobile stationinternational subscriber directory number (MSISDN) which is a mobilecommunication number of the UE. In addition, the above message mayinclude an indication of member addition/removal with respect to theexternal ID or the MSISDN. Also, the group management request messagemay include an indication that indicates whether to configure groupmanagement related data only up to the HSS 115 or up to the MME 105.

If there are two or more group management request messages, a relativepriority scheme for deciding which message will be processed first maybe used, and this may comply with setting values of the SCEF 120.

If the group management type indicates the group creation, the externalgroup ID should be associated with the external IDs or MSISDNs of theUEs to be included in a new group identified by the external group ID.If the group management type indicates the group modification, theexternal group ID should be associated with the external IDs or MSISDNsof the UEs each of which is to be added to or removed from the existinggroup identified by the external group ID. Also, each of the externalIDs or MSISDNs should be associated with the member addition/removalindication. If the group management type indicates the group removal,the external group ID should not be associated with any external ID orMSISDN, and the external group ID may indicate the existing group to beremoved.

Meanwhile, the group management request message may include at least oneof the external ID and the MSNID, which can be used by the HSS 115 tomanage a group ID list. Using the external ID or MSN ID included in thegroup management request, the HSS can easily find the UE to be removedfrom the group list.

At operation 153, the SCEF 120 may store at least one of the SCS/AS IDand the SCS/AS reference ID which are received at operation 151. TheSCEF 120 may assign an SCEF reference ID in order to indicate theconnection with the SCS/AS 125 and use it for the connection with theHSS 115. Based on mobile communication operator's policies, if theSCS/AS 125 is not authorized to perform the group management request,the group management request is not performed. Also, if the groupmanagement request is malfunctioning, or if the SCS/AS 125 sends thegroup management request message more than its quota, the SCEF 120 maytransmit a group management response message to the SCS/AS 125 atoperation 161 to inform a rejection message and its cause.

At operation 155, the SCEF 120 transmits the group management requestmessage to the HSS 115 to configure group-related information in the HSS115. This message may include an SCEF ID and an SCEF reference ID foridentifying a connection between the SCEF and the HSS in addition to thegroup management type and the external group ID both of which arereceived at the operation 151. In addition, the above message mayinclude the member addition/removal indication and an external ID orMSISDN of each UE. Also, the group management request message mayinclude an indication that indicates whether to configure groupmanagement related data only up to the HSS 115 or up to the MME 105.

Meanwhile, the operation 155 may be performed for a policy chargingresource function (PCRF).

At operation 157, the HSS 115 checks the group management requestmessage received at the operation 155, for example, checks whether theHSS 115 supports the group management request, whether the externalgroup ID exists, whether the external ID or MSISDN exists, and whetherthe MME/SGSN supports a group management function. If this check fails,the HSS 115 notifies a failure to the SCEF 120 at operation 159 and mayalso provide a failure reason.

If the above check is successful, the HSS 115 may store the SCEF ID andthe SCEF reference ID. The HSS 115 may modify the group ID list ofsubscriber data of the UE, as follows. The group ID list may indicate agroup ID-list field already existing in subscriber data/mobilitymanagement (MM) context or may indicate a new field.

If the group management type indicates the group creation, the HSS 115allocates a new group ID. This new group ID may be associated with theexternal group ID or any other group ID used in the mobile communicationnetwork. The allocated new group ID is added to the group ID list of thesubscriber data of the UE(s).

If the group management type indicates the group modification, the HSS115 derives a group ID, used in the mobile communication network, fromthe external group ID, and adds or removes the derived group ID to orfrom the group ID list of the subscriber data of the UE to configureaddition/removal of the UE in a specific group.

If the group management type indicates the group removal, the HSS 115derives a group ID, used in the mobile communication network, from theexternal group ID, identifies UEs which are members of a relevant group,and removes the derived group ID from the group ID list of thesubscriber data of the identified UEs. Also, the HSS 115 removes theexternal group ID. Using the external ID or MSN ID included in the groupmanagement request, the HSS 115 can easily find the UE to be removedfrom the group list.

At operation 159, the HSS 115 transmits a group management responsemessage to the SCEF 120 to notify acceptance or rejection of the groupmanagement request. At operation 161, the SCEF 120 transmits the groupmanagement response message to the SCS/AS 125 to notify acceptance orrejection of the group management request. The operations 159 and 161may be performed after operation 173. In this case, operations 175 and177 may be omitted.

At operation 163 or 169, the MME/SGSN 105 serving the UE(s) is affectedby the group management request.

At operation 163, the HSS 115 may transmit an insert subscriber datarequest message for updating subscriber data of the UE to the MME/SGSN105 that supports a group-based subscriber data update. When receivingthe insert subscriber data request message, the MME/SGSN 105 performsoperations 165 and 167. At operation 169, the HSS 115 may transmit aninsert group data request message for updating subscriber data of UEsbelonging to a relevant group to the MME/SGSN 105 that supports agroup-based subscriber data update. When receiving the insert group datarequest message, the MME/SGSN 105 performs operations 171 and 173. Theinsert subscriber data request message or the insert group data requestmessage may include IDs of UEs affected by the group management request,based on the number of UEs belonging to the group or the number of UEsserved by the MME/SGSN 105 among the UEs belonging to the group (theinsert group data request message is a new message proposed in anembodiment of the present invention).

The HSS 115 may transmit the insert subscriber data request message tothe MME/SGSN 105 that does not support a group-based subscriber dataupdate.

At operation 165 or 171, the MME/SGSN 105 verifies the message receivedat the operation 163 or 169. If the message relates to information abouta public land mobile network (PLMN) other than a home PLMN (HPLMN), theMME/SGSN 105 may verify whether the group management function isincluded in a roaming agreement. If not included, the MME/SGSN 105 maynotify a failure to the HSS 115. Also, based on mobile communicationoperator's policies, the MME/SGSN 105 may reject the request in case ofa congestion situation or when the group management request occursfrequently or exceeds its quota.

At operation 167 or 173, the MME/SGSN 105 updates the subscriber data ofUE and then transmits an answer message to the HSS 115. The answermessage may indicate several UEs belonging to the group. For example, aninsert group data answer message including international mobilesubscriber IDs (IMSI) of UEs served by the MME/SGSN 105 among groupmember UEs may be transmitted.

At operation 175, the HSS 115 that receives the answer transmits a groupmanagement confirm message to the SCEF 120.

At operation 177, the SCEF 120 transmits the result of the groupmanagement request to the SCS/AS 125.

Second Embodiment

The second embodiment of the present invention relates to a method forefficiently controlling a plurality of terminals (UEs) and to anapparatus for performing the method.

FIG. 2 is a diagram illustrating a monitoring event configurationprocedure according to a second embodiment of the present invention.Proposed in this embodiment is a method for performing group-basedmonitoring event configuration/report as part of monitoring eventconfiguration/report functions defined in 3GPP. Common parameters andevent types are detailed in clauses 5.6.1.2 and 5.6.1.3 to 5.6.1.9 of TS23.682.

The procedure of FIG. 2 may be performed to replace or delete amonitoring event configuration and also be performed to configure amonitoring event for one-time reporting.

Referring to FIG. 2, a mobile communication system may include anMME/SGSN 205, an HSS 215, an SCEF 220, and an SCS/AS 225. The MME orSGSN 205 may be an entity for managing the mobility of UE and is anentity for collecting monitoring information and reporting it to the HSS215.

At operation 251, the SCS/AS 225 transmits a monitoring request messageto the SCEF 220. The monitoring request message may include at least oneof external identifier(s) or MSISDN(s), an SCS/AS identifier, an SCS/ASreference ID, a monitoring type, the maximum number of reports, amonitoring duration, a monitoring destination address, an SCS/ASreference ID for deletion, an external group ID, and a wait time forSCEF, HSS, and/or CN node. The wait time may be called a waiting time.The external group ID indicating an ID of a group to which the UEbelongs may be a value associated with an external ID for identifyingthe UE or an MSISDN which is a mobile communication number of the UE.

Here, the wait time for SCEF, HSS, and MME/SGSN refers to a time forwhich a relevant network apparatus collects monitoring event results ofthe UE belonging to the group. In other words, there may be a pluralityof UEs managed by one network apparatus, and among them there may be twoor more UEs which are members of the external group ID. When amonitoring event occurs at one of the UEs, the apparatus does not send areport on the result of the event immediately, but collects themonitoring event results of the UEs belonging to the group for aspecific time and then sends a report. This specific time means the waittime. That is, this may be called a guard timer to send a monitoringreport for the group. This timer is stored in the SCEF 220 and the HSS215 and may be used when each node processes the received monitoringevent result. Also, the MME/SGSN 205 may store this timer and use it toprocess the monitoring event result. If the group ID is included in themonitoring request message, the individual identifier of the UE may notbe included. Also, the monitoring request message may include both agroup ID and an individual identifier of the UE.

If there are two or more group management request messages, a relativepriority scheme for deciding which message will be processed first maybe used, and this may comply with setting values of the SCEF.

At operation 253, the SCEF 220 may store at least one of the SCS/AS ID,the SCS/AS reference ID, the monitoring destination address, themonitoring duration, the maximum number of reports, and the wait timewhich are received at the operation 251. The SCEF 220 may assign an SCEFreference ID in order to indicate the connection with the SCS/AS 225 anduse it for the connection with the HSS 215. Based on mobilecommunication operator's policies, if the SCS/AS 225 is not authorizedto perform the monitoring request, the monitoring request is notperformed. Also, if the monitoring request is malfunctioning, or if theSCS/AS 225 sends the monitoring request message more than its quota, theSCEF 220 may transmit a monitoring response message to the SCS/AS 225 atoperation 267 to inform a rejection message and its cause.

The SCEF 220 stores the received wait time value and, when performing amonitoring event reporting, may collect the monitoring event results ofthe UEs belonging to the group for the wait time. After the expirationof the wait time, the SCEF 220 may deliver a monitoring report as asingle message to the SCS/AS 225.

At operation 255, the SCEF 220 sends the monitoring request message tothe HSS 215. This message may include at least one of a UE identifier orUE group identifier, an SCEF ID which is an identifier of the SCEF, anSCEF reference ID for identifying a connection between the SCEF and theHSS, a monitoring type for indicating the type of a monitoring event,the maximum number of reports that can be sent, a monitoring duration,and a wait time. The wait time may be stored in the HSS 215 or theMME/SGSN 205. The monitoring duration refers to a period during whichmonitoring is performed. During the monitoring duration, the monitoringreports of group members are collected from the first occurrence of themonitoring event for the UE in the group to the expiration of the waittime, and then sent at a time. The wait time starts again immediately orwhen a group member's monitoring event occurs. This is done within themonitoring duration, and if the monitoring duration expires, no furthermonitoring is performed.

At operation 257, the HSS 215 checks the monitoring request messagereceived at the operation 255, for example, checks whether the HSS 215supports a monitoring event function, whether the external group IDexists, whether the external ID or MSISDN exists, whether the MME/SGSNsupports the monitoring event function, or whether the monitoring eventthat should be deleted is valid. If this check fails, the HSS 215notifies a failure to the SCEF 220 at operation 265 and may also providea failure reason.

If the above check successful, the HSS 215 may store at least one of theSCEF ID, the SCEF reference ID, the maximum number of reports, themonitoring duration, the SCEF reference ID for deletion, and the waittime (for HSS). For monitoring event reporting, the HSS 215 may use thewait time. Details of the wait time are as described above at theoperation 255.

At operation 259, the HSS 215 may configure a required monitoring typeto the MME/SGSN 205. For this, the HSS 215 sends an insert subscriberdata request message to the MME/SGSN 205. Alternatively, the HSS 215 maysend an insert group data request as a single message to two or more UEswhich are group members. This message may include identifiers of UEsserved by the MME/SGSN 205 among UEs belonging to the group. The insertsubscriber data request message or the insert group data request messagemay include IDs of UEs affected by the group management request, basedon the number of UEs belonging to the group or the number of UEs servedby the MME/SGSN 205 among the UEs belonging to the group.

At operation 261, the MME/SGSN 205 may be configured to use aninterworking SCEF (IWK-SCEF), which is a network apparatus used for aconnection with the SCEF of another PLMN. Thus, the IWK-SCEF is anapparatus for delivering information, received from the SCEF, to theMME/SGSN 205 in its PLMN, or delivering information, received from theMME/SGSN 205 in its PLMN, to the SCEF of another PLMN.

The MME/SGSN 205 verifies whether the monitoring type is supported by aroaming agreement, or whether deletion is possible for the SCEFreference ID for deleting monitoring event configuration. If thisverification fails, the MME/SGSN 205 provides a failure message and itsreason to the SCEF 220 or the IWK-SCEF at operation 263.

The MME/SGSN 205 stores the received parameters and starts to watch forthe indicated monitoring event. If the monitoring event requests aone-time report, a monitoring report may be included in an answer to themessage of the operation 259. In this case, after waiting for the waittime and confirming the monitoring events of the UEs belonging to thegroup, the monitoring report may be delivered by constructing a messagein response to the operation 259 to include the identifiers of UEsbelonging to the group.

The MME/SGSN stores, as context, parameters for monitoring configured inthe above procedure, and may deliver it whenever the MME/SGSN changes.

If the monitoring configuration is successful, the MME/SGSN 205 sends ananswer message to the HSS 215 at operation 263. This answer message maybe an insert subscriber data answer or insert group data answer. If agroup of subscriber data insert requests are received from the HSS, thisanswer may be a reply to the group. If the monitoring event occursbefore sending the answer message, the monitoring event result may beincluded in the answer message.

At operation 265, the HSS 215 sends a response message to the monitoringrequest to the SCEF 220. This message includes a result of processingthe monitoring request. If the monitoring event configuration is aone-time monitoring, the HSS 215 deletes the monitoring eventconfiguration after processing the monitoring report. Also, the waittime may be deleted.

If the UE moves to another region, the HSS 215 may determine whether theMME/SGSN 205 serving the UE in that region supports a group-basedmonitoring event. If not supported, it is impossible to perform agroup-based monitoring operation for the UE belonging to the region.Therefore, the HSS 215 may notify, to the SCEF 220, information aboutthe UE belonging to the region of the MME/SGSN 205 that does not supportthe group-based monitoring event. Or the following operation 267 (a) or(b) may be performed.

At operation 267, the SCEF 220 sends a monitoring response message tothe SCS/AS 225. If the monitoring result report is received at theoperation 265, this is included in the above message. If there is themonitoring report received before the monitoring response arrives fromthe HSS 215, this may be collected and then included in the monitoringresponse to be transmitted to the SCS/AS 225. Or the monitoring reportsmay be collected during the wait time and then included in themonitoring response to be sent to the SCS/AS 225.

If the HSS 215 fails to support a group-based monitoring event or aspecific monitoring event with regard to the current MME/SGSN servingthe UE, e.g., if the UE moves to a region of the MME/SGSN, the HSS 215may perform the following operation (a) or (b).

(a) The HSS 215 notifies the SCEF that the configured monitoring eventis cancelled. Also, the HSS 215 deletes the configured monitoring event.And also, the HSS 215 may provide an indication called “retry after” tothe SCEF. This means to try the monitoring event configuration againlater. When this information is transmitted to the SCEF 220, the SCEF220 may send this information to the SCS/AS 225 to perform a monitoringevent configuration request again later.

(b) The HSS 215 notifies the SCEF 220 that the configured monitoringevent is suspended. The SCEF 220 interprets this to mean that thenetwork is temporarily unable to support the configured monitoringevent. Thereafter, if the MME/SGSN 205 changes, and if the new MME/SGSN205 can support the suspended monitoring event, the HSS 215 configuresthe new MME/SGSN with the suspended monitoring event and notifies theresumption of the suspended monitoring event to the SCEF 220. If aperiod of sending the monitoring report expires while the monitoringevent is suspended, the HSS 215 and the SCS/AS 225 delete the monitoringevent.

FIG. 3 is a diagram illustrating a monitoring event reporting procedurein an embodiment of the present invention.

Referring to FIG. 3, a system may include an MME/SGSN 305, an HSS 315,an SCEF 320, and a monitoring destination node 330. This embodiment ofFIG. 3 may provide a method of delivering a monitoring report for agroup when reporting the result of a monitoring event. The monitoringdestination node 330 may be an SCS/AS.

At operation 351 or 353, a monitoring event may be detected by a node atwhich the monitoring event is configured. The monitoring event may bedetected by the MME/SGSN 305 at the operation 351 or by the HSS 315 atthe operation 353.

Operation 355 is a case where the MME/SGSN 305 directly sends themonitoring report to the SCEF 320. At the operation 355, the MME/SGSN305 delivers a report for the detected monitoring event to the SCEF 320.The MME/SGSN 305 may deliver a monitoring indication message to the SCEF320, and this indication message may include an SCEF reference ID and amonitoring event report. At this time, the monitoring event report mayinclude information about UE for which the monitoring event is detected.The SCEF 320 may receive this message and determine which monitoringevent report of which UE. In this case, the MME/SGSN 305 may collect themonitoring reports of other UEs belonging to the group during the waittime provided in the monitoring configuration procedure after the firstmonitoring event occurs, and then send the collected monitoring reportsat a time after the expiration of the wait time.

Operation 357 is a case where the MME/SGSN 305 delivers the monitoringreport to the HSS 315. The MME/SGSN 305 may deliver the monitoringindication message to the HSS 315, and this indication message mayinclude an SCEF reference ID, a monitoring event report set, and a groupID or IMSI(s). If the monitoring event is requested based on the group,the MME/SGSN 305 may deliver the monitoring indication message forsending the monitoring report with regard to the group. Therefore, themonitoring indication message includes the group ID or IMSI which is theID of UE which is a group member. One or more IMSIs may be included.Also, the monitoring report of this message indicates that themonitoring report relates to a group-based monitoring event. In thiscase, the MME/SGSN may collect the monitoring reports of other UEsbelonging to the group during the wait time provided in the monitoringconfiguration procedure after the first monitoring event occurs, andthen send the collected monitoring reports at a time after theexpiration of the wait time.

At operation 358, the HSS 315 that receives the monitoring indicationmessage checks that the report is for which group and which monitoringevent, and then delivers it to the SCEF 320. In this case, the HSS 315may collect the monitoring reports of other UEs belonging to the groupduring the wait time provided in the monitoring configuration procedureafter the monitoring report is received from the MME/SGSN 305, and thensend the collected monitoring reports to the SCEF 320 at a time afterthe expiration of the wait time.

Operation 361 is a case where the HSS 315 that detects the monitoringevent configures the monitoring report and sends it to the SCEF 320. TheHSS 315 may send a monitoring indication message to the SCEF 320. If themonitoring event of UE belonging to the group is detected, the HSS 315may collect monitoring events of other UEs or additional monitoringevents of the same UE during the wait time, and then send the collectedmonitoring reports to the SCEF 320 at a time after the expiration of thewait time. At this time, it is possible to include the external group IDfor identifying the group and the external ID or MSISDN for identifyingthe UE for which the monitoring event is found. If the monitoring eventsoccur for all UEs in the group, only the external group ID may beincluded without the individual identifier of the UE when the monitoringreport is transmitted to the SCEF. The SCEF 320 may interpret this asthe occurrence of event for all UEs.

At operation 363, the SCEF 320 may deliver the received message to themonitoring destination node 330. The monitoring destination node 330 maybe the SCS/AS. At this time, the SCEF 320 may collect the monitoringreports for other UEs belonging to the group during the wait time afterthe monitoring report is received from the HSS. After the expiration ofthe wait time, the SCEF 320 delivers the collected monitoring reports tothe SCS/AS together with the external group ID for indicating the groupand the external ID or MSISDN of the UE for which the monitoring eventoccurs. If the monitoring events occur for all UEs in the group, onlythe external group ID may be included without the individual identifierof the UE when the monitoring report is sent to the SCS/AS. The SCS/ASmay interpret this as the occurrence of event for all UEs.

FIG. 4 is a diagram illustrating a communication pattern parameterprovisioning procedure according to an embodiment of the presentinvention.

Referring to FIG. 4, a communication system may include an MME 405, anHSS 415, an SCEF 420, and an SCS/AS 425.

A communication pattern (CP) parameter described in this embodiment ofFIG. 4 is as shown in Table 1.

TABLE 1 CP parameter Description 1) Periodic Identifies whether the UEcommunicates communication periodically or not, e.g. only on demand.[optional] indicator 2) Communication Duration interval time of periodiccommunication duration time [optional, may be used together with 1)]Example: 5 minutes 3) Periodictime Interval Time of periodiccommunication [optional, may be used together with 1)] Example:everyhour 4) Scheduled Time zone and Day of the week when the UE iscommunication available for communication [optional] time Example: Time:13:00-20:00, Day: Monday 5) Stationary Identifies whether the UE isstationary or indication mobile [optional]

At operation 451, the SCS/AS 425 sends an update request message to theSCEF 420. The update request message may be a message for updating orconfiguring a communication pattern. In order to configure thecommunication pattern, the SCS/AS 425 may request the SCEF 420 by usingthe external group ID which is the group ID to which the UE belongs.

At operation 453, the SCEF 420 may select a communication pattern or acommunication pattern parameter. After authenticating the request of theSCS/AS at the operation 451, the SCEF 420 may select the communicationpattern parameter. When several communication pattern parameters areactive for one UE, the SCEF may set different activation patterns to benot overlapped with each other.

At operation 455, the SCEF 420 may send a communication pattern (CP)parameter update request message (or update CP parameter request) to theHSS 415. The pattern parameter update request message includes theexternal group ID, and may request to configure the communicationpattern for the UEs belonging to the group.

At operation 457, the HSS 415 may update subscription information of theUE. The HSS 415 may check the CP parameter update request by usinginformation such as the External ID or MSISSN. If the check fails, theHSS may send a response for informing the failure to the SCEF 420 atoperation 459.

If the check is successful, the HSS 415 may update information of theUE, based on the CP parameter update request. The HSS 415 may store theCP parameters and may deliver them to the MME 405.

At operation 459, the HSS 415 may send a CP parameter response message(or update CP parameter response) to the SCEF 420. The CP parameterresponse message may include a SCEF reference ID and informationindicating the success or failure of the update.

At operation 461, the SCEF 420 may send an update response message tothe SCS/AS 425. The response message may include the SCEF reference IDand the information indicating the success or failure of the update.Through the response message, the SCEF may inform the SCS/AS whetherprovision of the CP parameter is successful.

At operation 463, the HSS 415 may initiate an insert subscription/groupdata procedure for the MME 405 and provide information about the CPparameter. The MME may confirm that information about the existing CPparameter is modified, delete the CP parameter, and store the new CPparameter.

Third Embodiment

The third embodiment of the present invention relates to a method andapparatus for providing a service of a roaming network.

FIG. 5 is a diagram illustrating a structure of a communication systemfor a terminal or a machine type communication (MTC) apparatus accordingto an embodiment of the present invention. FIG. 6 is a diagramillustrating architecture for service capability exposure according toan embodiment of the present invention. FIG. 7 is a diagram illustratingroaming architecture for service capability exposure according to anembodiment of the present invention.

In the third embodiment of the present invention, an entity, aconnection relationship, an interface, architecture of HPLMN and visitedpublic land mobile network (VPLMN), and a service capability exposure,which are described in the communication system structure of FIGS. 5, 6and 7, may be used.

When the UE is a roaming UE, it is necessary to know the HPLMN ID of theUE in order to know whether the SCEF can provide a service to theroaming UE. This is because it is necessary to check whether MB2connection or Rx or Nt connection exists for roaming.

In the third embodiment, the SCS/AS may request the serving PLMN ID ofthe UE and check whether there is a connection with the correspondingPLMN. If the IP address of the UE is within the range determined by thespecific PLMN, it is possible to confirm the corresponding roamingagreement or the connection with the roaming network by identifying thePLMN to which the UE belongs. Based on this, the SCS/AS makes a requestto the SCEF, and the SCEF may confirm whether there is a networkapparatus connected to the PLMN.

FIG. 8 is a diagram illustrating a group message delivery procedureusing multimedia broadcast/multicast services (MBMS) according to anembodiment of the present invention.

Referring to FIG. 8, a communication system may include a UE 805, aradio access network (RAN) 810, an MBMS gateway (MBMS-GW)/gateway GPRSsupport node (GGSN) 815, an MME/SGSN 815, a broadcast multicast servicecenter (BM-SC) 820, an HSS/home location register (HLR) (HSS/HLR) 825,an SCEF 830, and an SCS/AS 835.

At operation 851, the SCS/AS 835 sends a temporary mobile group identity(TMGI) allocation request message (or allocate TMGI request) to the SCEF530. The TMGI allocation request message may include an external groupID, an SCS identifier, and location/area information. The location/areainformation is information indicating the location/area of the UE. Whensending a message at the operation 851, the SCS/AS 830 may transmit thelocation/area information of the UE together. Based on a location/areaidentified from the location/area information, the SCEF 830 may derive acorresponding PLMN ID.

At operation 853, the SCEF 830 performs authorization with the HSS/HLR825. The SCEF 830 checks whether the SCS/AS 835 is authorized to performTMGI allocation. The SCEF 830 may derive the PLMN ID from thelocation/area information received at the operation 851. Based on this,the SCEF 830 may check whether there is an interface such as MB2 or T7with a network apparatus of the corresponding PLMN. If the check fails,the SCEF 830 sends a rejection message to the SCS/AS 835, and thismessage may include a reason for the rejection.

At operation 855, a TMGI allocation procedure may be initiated betweenthe SCEF 830, the HSS/HLR 825, and the BM-SC 820. This procedure isspecified in TS 23.468.

At operation 857, the SCEF 830 sends a TMGI assignment response message(or allocate TMTI response) to the SCS/AS 835. The SCEF 830 may transmitthe allocated TMGI and expiration time information.

Application level interactions may be performed at operation 851.

At operation 861, the SCS/AS 835 may send a group message requestmessage to the SCEF 830. The group message request message may includeat least one of an external group identifier, an SCS identifier,location/area information, RAT(s) information, TMGI, and a start time.The location/area information may be geographical location/areainformation.

At operation 863, the SCEF 830 and the HSS/HLR 825 may perform anauthorization operation. The SCEF 830 checks whether the SCS/AS 835 isauthorized to send a group message. The SCEF 830 may derive the PLMN IDfrom the location/area information received at the operation 851. Basedon this, the SCEF 830 may check whether there is an interface such asMB2 or T7 with a network apparatus of the corresponding PLMN. If thecheck fails, the SCEF 830 sends a rejection message to the SCS/AS 835,and this message may include a reason for the rejection.

At operation 865, the SCEF 830 may send an MBMS bearer activationrequest message (or activate MBMS bearer request) to the BM-SC 820. TheMBMS bearer activation request message may include an MBMS broadcastarea, a TMGI, a QoS, and a start time.

At operation 867, the BM-SC 820 performs a session start procedure. Thisprocedure is specified in TS 23.246.

At operation 869, the BM-SC 820 sends an MBMS bearer response message(or activate MBMS bearer response) to the SCEF 830.

At operation 871, the SCEF 830 may send a group message confirmationmessage (or group message confirm) to the SCS/AS 835. The group messageconfirmation message may indicate whether the request at the operation861 is accepted.

Application level interactions may be performed at operation 873.

At operation 875, the SCS/AS 835 may send, to the SCEF 830, content tobe delivered to the group. The content may be delivered to the UE 805via the BM-SC 820 and the RAN 810.

At operation 877, the UE 805 may perform a response action. The responseaction may be performed immediately or after a certain time elapses.

Fourth Embodiment

The fourth embodiment of the present invention relates to a method ofcommunication via a path suitable for a service characteristic and to anapparatus for performing the method.

FIG. 9 is a diagram illustrating architecture of a radio access networkand a core network according to an embodiment of the present invention.

In the pre-release 14 architecture, a dedicated core (DECOR) forenabling the UE to access a specific core network, and an SCEF foropening and negotiating the capability of a mobile communication networkfor an IoT service have been introduced.

Using this, the network architecture as shown in FIG. 9 may beconstructed. In FIG. 9, “d” denotes dedicated.

FIG. 10 is a diagram illustrating architecture of a radio access networkand a core network according to another embodiment of the presentinvention.

In the release 14 architecture, a control plane and a user plane ofgateway (GW) are distinguished from each other, so that asoftware-defined network (SDN) concept may be applied to the networkarchitecture. In addition, an eDecor is proposed as an improvedmechanism for connecting the UE to the dedicated core, and a group basedenhancement for efficiently managing a large number of IoT devices maybe proposed. Also, vertical services such as sponsored charging, whichallows a third-party provider to charge for data transmission andreception with a specific application, and vehicle to everything (V2X)may be supported in the mobile communication network.

If the release 14 architecture as shown in FIG. 10 is applied, the 3GPPnetwork may be structured as described above. A traffic detectionfunction (TDF) may analyze a traffic transmitted to the UE and determinea service type and a packet type (voice, video, etc.).

FIG. 11 is a diagram illustrating architecture of a radio access networkand a core network according to still another embodiment of the presentinvention.

Implementation based on the release 14 features may be as shown in FIG.11. That is, the GW of the 3GPP network may have a full SDN structure,and all user planes may be replaced with network resources. Those thattransmit data to the UE and store data of the UE may be configureddifferently from an SDN controller that controls the data transmissionof the UE.

FIG. 12 is a diagram illustrating architecture of a radio access networkand a core network according to yet another embodiment of the presentinvention.

Beyond the release 14, the network architecture may be developed asshown in FIG. 12. As the SCEF becomes more usable, it is possible toprovide a service by coordinating external network and internal networkinformation to enable a content delivery network (CDN). In addition, aconnection with a network apparatus for providing a V2X service may actas a window for connecting an external V2X server and a mobilecommunication network. Also, the SCEF may interact with a server havingexternal sponsored subscription information and thereby connect with anetwork function responsible for charging UE so that a data service ofthe specific UE can be used free of charge. In another user scenario, itis possible to realize a CriC service that communicates with a lowlatency through a data path optimization based on UE locations. This isbecause the location information of the UE can be shared with the insideand outside of the mobile communication through the SCEF and thus it ispossible to set a data path closest to the UE.

When SDN is activated, the following functions may be performed throughthe SCEF.

Service detection: The TDF may check packets transmitted/received by theUE and determine which service is used by the UE through the SCEF. ThePCRF may configure relevant information to the SDN controller to providethe optimized service.

Service categorization: The SCEF may inform the TDF about the type oftraffic to be used by the UE, based on information provided by theapplication server or external server, thereby allowing the applicationserver or third-party provider to charge data of the UE. Also, the SCEFmay grasp information provided by the application server or externalserver and notify it to the SDN controller to set a data transfer pathto the UE (Path definition, path provision).

The SCEF is an abbreviation of Service Capability Exposure Function, andrefers to a network function of exposing a mobile communication networkfunction and capability to the inside/outside and exchanginginformation.

Fifth Embodiment

The fifth embodiment of the present invention relates to a method ofcommunication of service contents distributed near a user and to anapparatus for performing the method.

FIG. 13 is a diagram illustrating a scheme of activating a contentsdeliver network (CDN: technique of deploying traffic to be delivered toUE near UE for smooth data communication) by using SCEF.

Referring to FIG. 13, a system of the fifth embodiment may include a UE1305, an access 1310, a 3GPP network 1315, an SCEF 1320, and an SCS/AS1325.

The SCS/AS 1325 or third party 1325 provides a service to the UE andexchanges data therefor. The SCS/AS 1325 may grasp location informationor service information of the UE through the service provided to the UE.

At operation 1351, the SCS/AS 1325 or the 3rd party 1325 may have a needfor the relocation of a data path to the UE. For example, it may bedecided that the UE has moved to another area and there is a data centerclose to the area. Also, in the expectation that the amount of data tobe used by the UE will increase in a current area of the UE, it ispossible to make a decision to deploy a server capable of processinglarge capacity data at the current UE location so as to provide, forexample, high-quality video streaming.

At operation 1353, the SCS/AS 1325 or the third party 1325 may send arequest to the SCEF 1320 to relocate the data path of the UE. Thismessage for the request may be a data relocation request. This mayinclude a current location of the UE, the amount of data to be used bythe UE, or a data center address to be provided to the UE.

At operation 1355, the SCEF 1320 that receives the request may checkwhether the SCS/AS 1325 or the third party 1325 is authorized to makesuch a request and to request a change of network information. Then, theSCS/AS 1325 or the third party 1325 sees the location informationrequested according to the above procedure and establishes a data pathof the UE to a user plane resource, i.e., gateway, near the current UElocation and the data center so that the UE can perform high-speed,large-capacity communication with the data center being at the location.In other words, it is possible to deploy the data path of the UE to aswitch or router near a specific data center so that the UE can accessthe data center more quickly, or it is possible to deploy ahigh-capacity switch or router for the data path of the UE so that theUE can exchange data with the data center at a higher speed.

Thereafter, the SCEF 1320 sends a response message to the SCS/AS 1325 orthe third party 1325 at operation 1357. This response message may be adata relocation response. The response message may include an SCC/ASreference ID, a response reason, and CN node information.

The SCS/AS 1325 or the third party 1325 that receives the responsetransfers data partially to the SCEF 1320 at operation 1361. This is anIP packet of data to be relocated, and thus may include an IP address ofthe UE.

At operation 1363, the SCEF 1320 may identify the IP of the UE and theIP of the data server through this packet, and check whether theconnection is provided in its mobile communication network. At operation1365, the SCEF 1320 may transfer the packet to the 3GPP network 1315.The SCEF 1320 may negotiate with a 3GPP network apparatus to establishthe data path to the optimal location. In this case, the target 3GPPnetwork apparatus may negotiate for at least one of a policy function, asession management function, and a mobility management function.

At operation 1367, the 3GPP network 1315 that authenticates the IP forthe UE according to the negotiation with the SCEF establishes theoptimal data path by considering the location of the UE and the locationof the data server. That is, the optimal user plane function is selectedto relocate the data session. Using the data path, the UE transmits andreceives data.

At operation 1371, the SCS/AS 1325 or the third party 1325 may provideCN node information to the UE 1305.

At operation 1373, the UE 1305 may send a data request message to the3GPP network 1315. The data request message may include informationabout the UE IP address. At operation 1375, the 3GPP network 1315 mayperform authorization for the UE. Depending on the authorization result,the 3GPP network 1315 may send a data response message to the UE 1305 atoperation 1377. The data response message may include relocation data.

The SCEF 1320 is an abbreviation of Service Capability ExposureFunction, and refers to a network function of exposing a mobilecommunication network function and capability to the inside/outside andexchanging information.

Sixth Embodiment

The sixth embodiment of the present invention relates to a method for aUE to transmit and receive data by connecting to a plurality ofthird-party servers, and to an apparatus for performing the method.

In this embodiment of the present invention, CIoT represents an IoTservice using a cellular network. The cellular network refers to amobile communication network, including 2^(nd) generation (2G)represented by global system for mobile communication (GSM) enhanceddata rates for GSM (EDGE) radio access network (GERAN), 3^(rd)generation (3G) represented by GPRS, and 4th generation (4G) representedby LTE. The CIoT service refers to a cellular service for supporting anIoT device, and may refer to a service for transmitting a small amountof data through the cellular network. It may also include a machine typecommunication (MTC) service. The cellular network includes not only aradio access network but also a core network.

The embodiment of the present invention deals with the operations of aUE and a network apparatus for supporting IoT in the cellular network.Although the embodiment of the present invention is described on thebasis of the LTE system defined by 3GPP, it may be similarly usedthroughout the wireless communication such as wireless local areanetwork (WLAN) or Bluetooth. Proposed are in the present invention are amethod and apparatus for exchanging relay-related information between acore network and a base station (or evolved Node B (eNB)) in order tosupport a UE-to-network relay function, which is one of proximityservice (ProSe) functions for public safety, and a method and apparatusfor controlling the UE to support the relay function at the basestation.

An SCS/AS refers to a 3rd party application server.

An SCEF performs a function of connecting the SCS/AS and an EPS networkand is located in a trusted domain.

The SCEF is connected to an HSS and receives information about the UE.

The SCEF may be connected with an MME through the HSS and exchange data.

There are a UE-MME connection, a MME-SCEF connection, and a SCEF-SCS/ASconnection. Through these connections, data sent by the UE may bedelivered to the SCS/AS, and data send by the SCS/AS may be delivered tothe UE.

Therefore, a procedure of establishing the UE-MME connection, theMME-SCEF connection, and the SCEF-SCS/AS connection is required.

Sixth-First Embodiment

FIG. 14 is a diagram illustrating a configuration procedure forestablishing a data connection between an SCS/AS, an SCEF, and an MME inan embodiment of the present invention.

Referring to FIG. 14, a communication system of this embodiment mayinclude an MME 1405, an IWK-SCEF 1410, an HSS 1415, an SCEF 1420, and anSCS/AS 1425.

At operation 1451, the SCS/AS may send a non-IP data delivery (NIDD)configuration request message to the SCEF 1420.

At operation 1453, the SCEF 1420 may store information received throughthe NIDD configuration request and verify the SCS/AS 1425.

At operation 1455, the SCEF may send the NIDD configuration requestmessage to the HSS 1415. This message may include an external ID, anSCEF ID, and an SCEF reference ID.

At operation 1457, the HSS 1415 may verify the validity for datadelivery by using the received NIDD configuration request message.

At operation 1459, the HSS 1415 sends an insert subscriber data requestmessage to the MME 1405. This message may include an IMSI, the SCEF ID,and the SCEF reference ID.

If the MME 1405 is configured to use the IWK-SCEF 1410, the MME 1405sends an inform IWK-SCEF message to the IWK SCEF 1410 at operation 1461.

At operation 1463, the IWK-SCEF 1410 may verify the request and notify averification result.

If the verification is successful, the IWK-SCEF 1410 may send anauthorization from IWK-SCEF message to the MME 1405 at operation 1465.

At operation 1467, the MME 1405 may verify the request.

At operation 1469, the MME 1405 may send an insert subscriber dataanswer message to the HSS 1415. The MME 1405 may use the SCEF referenceID later in data transmission.

At operation 1471, the HSS 1415 may send an NIDD configuration responsemessage to the SCEF 1420. This message may include the SCEF reference IDand an MME address.

At operation 1473, the SCEF 1420 may send the NIDD configurationresponse message to the SCS/AS 1425. This message may include an SCS/ASreference ID.

Meanwhile, when multiple SCS/ASs are connected to a single UE atoperations of FIG. 14, the SCEF creates one external ID or one SCEFreference ID per SCS/AS reference ID for the SCS/AS-SCEF-MME-UEconnection.

Therefore, when multiple SCS/ASs are connected to the SCEF to establisha connection with a single UE, the SCEF is connected with the MME byusing multiple SCEF reference IDs corresponding to multiple SCS/ASs.Thus, the MME has multiple SCEF reference IDs for a single UE.

In this case, when the MME receives data from the UE, it is necessary toknow which SCEF reference ID will be used for delivering data to theSCEF. So, the SCEF can find a target SCS/AS corresponding to the SCEFreference ID and deliver data.

Proposed in the following embodiments is a method for the SCEF todeliver UE data (i.e., mobile originated) to a correct target SCS/ASwhen two or more SCS/ASs have data connections for a single UE via theSCEF.

Sixth-Second Embodiment

FIG. 15 is a diagram illustrating a method for utilizing an EPS bearerID at a terminal and an MME in an embodiment of the present invention.

Referring to FIG. 15, a communication system of this embodiment mayinclude a UE 1505, an eNB 1510, an MME 1515, an HSS 1520, and an SCEF1525.

In this embodiment of FIG. 15, the SCEF 1525 may receive a dataconnection establishment request from a plurality of SCS/ASs. This isidentified through an SCS/AS ID or an SCS/AS reference ID. The SCEF 1525may allocate an SCEF reference ID per the SCS/AS ID or the SCS/ASreference ID. The SCEF 1525 that performs the above procedure deliversat least one of the SCS/AS ID, the SCS/AS reference ID, the SCEF ID, orthe SCEF reference ID to the HSS 1520 at operation 1541, and the HSS1520 stores it and may deliver it to the MME 1515 at operation 1543(insert subscription data procedure). The insert subscription dataprocedure and data delivery configuration request/response may use thosedescribed in other embodiments.

In FIG. 15, a binding-related procedure may be performed immediatelyafter receiving a packet data network (PDN) connection request messageor immediately after sending a bearer setup message to the UE. The MME1515 acquires information related to the SCEF through negotiation withthe HSS 1520, and this is performed in the insert subscription dataprocedure. At operation 1545, the HSS 1520 sends a data deliveryconfiguration response message to the SCEF 1525. Through the datadelivery configuration request/response with the HSS, the SCEF 1525knows which MME 1515 is serving the corresponding UE.

The information related to the SCEF may include at least one of the SCEFID, the SCEF reference ID, the SCS/AS ID, the SCS/AS reference ID, andan external ID for the corresponding UE (IMSI).

At operation 1551, the UE 1505 establishes a radio resource control(RRC) connection with the eNB 1510 to send a message to the MME 1515.

At operation 1553, the UE 1505 transmits a PDN connection requestmessage to the MME 1515 to establish a data delivery connection with theSCEF 1525.

The PDN connection request may include at least one of a PDN type=SCEF,a data type=IP, non-IP, or other data format, an access point name(APN)=an APN value indicating SCEF connection, and an EPS bearer ID=abearer identifier to be used for SCEF connection by the UE. The APN maybe omitted. The PDN type may be represented by IP, non-IP, SMS, or SCEF.

At operation 1559, the MME 1515 performs binding with the EPS bearer IDby using the SCEF-related information acquired from the HSS 1520.

Binding the SCEF reference ID and the EPS bearer ID.

The above binding may include binding with at least one of the SCS/ASID, the SCS/AS reference ID, the SCEF ID, and the external ID which arereceived from the HSS.

Because of having this binding, the MME 1515 may identify the SCEFreference ID, the SCEF ID, etc. as to which SCEF connection is used fordelivering data sent by the UE via a specific EPS bearer ID. Further,the MME may identify the SCS/AS ID, the SCS/AS reference ID, etc. as towhich SCS/AS connection is used for data delivery, and deliver this tothe SCEF together with data sent by the UE. The SCEF may identify atarget SCS/AS from the received SCS/AS ID or SCS/AS reference ID anddeliver data.

After binding, the MME 1515 transmits a bearer setup message to the UE1505 at operation 1555 and establishes a bearer connection for an SCEFconnection.

The bearer setup message may include at least one of the followinginformation.

EPS bearer ID=An EPS bearer ID received from the UE or an EPS bearer IDnewly assigned by the MME.

APN=An APN received from the UE or an APN specified by the MME. Afterreceiving the APN, the UE may use it for delivering data of a specificapplication with a specific APN in the UE.

SCEF related Information=At least one of the SCEF reference ID or SCEFID for identifying the SCEF connection, the SCS/AS reference ID orSCS/AS ID for identifying the SCS/AS connections, and the external IDfor identifying the UE at the SCS/AS or SCEF may be included.

QoS=QoS is a value indicating the level of quality of service to beapplied by the UE to send data through the SCEF connection, and may be avalue indicating a connection priority, a maximum bitrate, a fixedbitrate, etc. of the established bearer.

At operation 1557, the UE 1505 that receives the bearer setup messagecan know that a connection for the SCEF is established with the EPSbearer ID, and completes the bearer connection establishment through theSCEF 1525 by sending a bearer setup complete message to the MME 1515.

Then, the UE 1505 can send data to the SCEF 1525 by using acorresponding bearer.

Data transmitted by the UE is referred to as mobile originated (MO)data. The UE 1505 may transmit data through a NAS message. The NASmessage refers to a message exchanged between the UE 1505 and the MME1515.

At operation 1561, the UE 1505 uses an uplink NAS transfer message totransmit MO data. This NAS message includes the following information.

EPS bearer ID: This is a value for identifying the MME-SCEF connectivityas to which SCEF is a target of data delivery from the MME.

SCEF related Information=At least one of the SCEF reference ID or SCEFID for identifying the SCEF connection at the MME, the SCS/AS referenceID or SCS/AS ID for identifying the SCS/AS connections at the SCEF, andthe external ID for identifying the UE at the SCS/AS or SCEF may beincluded.

Data payload: Actual data to be transmitted to the SCS/AS by the UE

Upon receipt of the message, the MME 1515 looks up the EPS bearer ID,finds binding information about which SCEF 1525 should be connected, andidentifies the SCEF reference ID or SCEF ID. At operation 1563, the MME1515 delivers the MO data to the corresponding SCEF 1525, and a messagefor delivering the MO data includes at least one of the followinginformation.

SCEF related Information=At least one of 1) the SCS/AS reference ID orSCS/AS ID for identifying the SCS/AS connection, 2) the external ID foridentifying the UE at the SCS/AS, and 3) the SCEF ID for indicating asource SCEF from which data is transmitted may be included.

Data payload: Actual data to be transmitted to the SCS/AS by the UE

At operation 1567, the SCEF 1525 may send, to the MME 1515, an ACK forindicating the completion of message reception. At operation 1565, theSCEF 1525 identifies a target SCS/AS through the received SCEF-relatedinformation. The SCEF 1525 delivers data received from the MME to thecorresponding SCS/AS.

Sixth-Third Embodiment

FIG. 16 is a diagram illustrating a method for utilizing a referenceidentifier of an SCEF or an identifier of an SCS/AS at a terminal in anembodiment of the present invention.

Referring to FIG. 16, a communication system of this embodiment mayinclude a UE 1605, an eNB 1610, an MME 1615, an HSS 1620, and an SCEF1625.

In this embodiment of FIG. 16, the SCEF 1625 may receive a dataconnection establishment request from a plurality of SCS/ASs. This isidentified through an SCS/AS ID or an SCS/AS reference ID. The SCEF 1625may allocate an SCEF reference ID per the SCS/AS ID or the SCS/ASreference ID. The SCEF 1625 that performs the above procedure deliversat least one of the SCS/AS ID, the SCS/AS reference ID, the SCEF ID, orthe SCEF reference ID to the HSS 1620 at operation 1641, and the HSS1620 stores it and may deliver it to the MME 1615 at operation 1643(insert subscription data procedure).

Contrary to the sixth-second embodiment, the sixth-third embodiment hasno procedure of allocating the EPS bearer ID.

At operation 1651, the UE 1605 establishes an RRC connection with theeNB 1610 to send a message to the MME 1615.

At operation 1653, the UE 1605 transmits a PDN connection request to theMME 1615 to establish a data delivery connection with the SCEF 1625.

The PDN connection request may include at least one of a PDN type=SCEF,a data type=IP, non-IP, or other data format, and an access point name(APN)=an APN value indicating SCEF connection. The APN may be omitted.The PDN type may be represented by IP, non-IP, SMS, or SCEF.

At operation 1659, the MME 1615 performs binding with a UE identifier(e.g., IMSI) by using the SCEF-related information acquired from the HSS1620.

Binding the SCEF reference ID and the UE identifier: It is possible toknow which SCEF reference ID is associated with the UE.

The above binding may include binding with at least one of the SCS/ASID, the SCS/AS reference ID, the SCEF ID, and the external ID which arereceived from the HSS.

Because of having this binding, the MME may identify, based on the UEidentifier, the SCEF reference ID, the SCEF ID, etc. as to which SCEFconnection is used for delivering data sent by the UE. Further, the MMEmay identify the SCS/AS ID, the SCS/AS reference ID, etc. as to whichSCS/AS connection is used for data delivery, and deliver this to theSCEF together with data sent by the UE. The SCEF may identify a targetSCS/AS from the received SCS/AS ID or SCS/AS reference ID and deliverdata.

After binding, the MME 1615 transmits a bearer setup message to the UE1605 at operation 1655 and informs information about a bearer connectionfor an SCEF connection.

The bearer setup message may include at least one of the followinginformation.

APN=An APN received from the UE or an APN specified by the MME. Afterreceiving the APN, the UE may use it for delivering data of a specificapplication with a specific APN in the UE.

SCEF related Information=At least one of 1) the SCEF reference ID orSCEF ID for identifying the SCEF connection at the MME, 2) the SCS/ASreference ID or SCS/AS ID for identifying the SCS/AS connections at theSCEF, and 3) the external ID for identifying the UE at the SCS/AS orSCEF may be included.

QoS=QoS is a value indicating the level of quality of service to beapplied by the UE to send data through the SCEF connection, and may be avalue indicating a connection priority, a maximum bitrate, a fixedbitrate, etc. of the established bearer.

The UE 1605 that receives the bearer setup message can know that aconnection for the SCEF is established with the SCEF-relatedinformation, and completes the bearer connection establishment throughthe SCEF 1625 by sending a bearer setup complete message to the MME1615.

Then, the UE 1605 can send data to the SCEF 1625 by using acorresponding bearer. Since there is no bearer identifier, the UE 1605should include an identifier indicating the SCEF connection in themessage. Through this identifier, the MME 1615 can know the data to betransmitted to the SCEF.

Data transmitted by the UE is referred to as mobile originated (MO)data.

The UE may transmit data through a NAS message. The NAS message refersto a message exchanged between the UE 1605 and the MME 1615.

At operation 1661, the UE 1605 uses an uplink NAS transfer message totransmit MO data. This NAS message includes the following information.

Connectivity type: This indicates that data is delivered via the SCEFconnection. Through this, the MME may know that a message includes datato be delivered to the SCEF.

SCEF related Information=At least one of the SCEF reference ID or SCEFID for identifying the SCEF connection at the MME, the SCS/AS referenceID or SCS/AS ID for identifying the SCS/AS connections at the SCEF, andthe external ID for identifying the UE at the SCS/AS or SCEF may beincluded.

Data payload: Actual data to be transmitted to the SCS/AS by the UE

Upon receipt of the message, the MME 1615 looks up the connectivity typeand knows that a message is for data to be connected with the SCEF.Also, the MME looks up the UE identifier (e.g., IMSI), finds bindinginformation about which SCEF should be connected, and identifies theSCEF reference ID or SCEF ID. Also, the MME looks up the SCEF-relatedinformation sent by the UE 1605 and identifies the target SCEF referenceID or SCEF ID. At operation 1663, the MME 1615 delivers the MO data tothe corresponding SCEF, and a message for delivering the MO dataincludes at least one of the following information.

SCEF related Information=At least one of 1) the SCS/AS reference ID orSCS/AS ID for identifying the SCS/AS connection, 2) the external ID foridentifying the UE at the SCS/AS, and 3) the SCEF ID for indicating asource SCEF from which data is transmitted may be included.

This information may include information in the NAS message receivedfrom the UE by the MME.

Data payload: Actual data to be transmitted to the SCS/AS by the UE

At operation 1667, the SCEF 1625 may send, to the MME 1615, an ACK forindicating the completion of message reception. At operation 1665, theSCEF 1625 identifies a target SCS/AS through the received SCEF-relatedinformation. The SCEF 1625 delivers data received from the MME 1615 tothe corresponding SCS/AS.

Sixth-Fourth Embodiment

The sixth-fourth embodiment is similar to the sixth-third embodiment,and is different in the procedure of transmitting the MO data at the UE.

A data payload transmitted to the SCEF by the UE includes the SCEFreference ID or the SCS/AS ID. The MME looks up the UE identifier (e.g.,IMSI) and thereby identifies the SCEF reference ID connected to the UE.Then, based on the SCEF reference ID, the MME delivers data receivedfrom the UE. The SCEF identifies the SCEF reference ID or the SCS/AS IDin the data payload and delivers the received data to the target SCS/AS.

Sixth-Fifth Embodiment

In the sixth-fifth embodiment of the present invention, when the SCEFhas connections with a plurality of SCS/ASs, the SCEF establishes aconnection with the MME, using one SCEF reference ID, by binding oneSCEF reference ID for a plurality of SCS/AS reference IDs.

The SCEF acquires the MSISDN of the UE when negotiating with the HSS,and can uniquely identify the UE.

Also, the SCS/AS may uniquely identify the UE by using a unique value ofthe external ID. Therefore, the SCEF may always identify the identicalUE through the external ID received from the SCS/AS. In this case, theexternal ID may be MSISDN.

The SCEF may receive a data connection establishment request frommultiple SCS/ASs. This may be identified from the SCS/AS ID or theSCS/AS reference ID. The SCEF may allocate one SCEF reference ID for allthe SCS/AS IDs or the SCS/AS reference IDs. The SCEF may deliver theSCEF reference ID to the HSS when negotiating with the HSS, and the HSSmay store it and then deliver it to the MME. At this time, the SCEF IDor address of the corresponding SCEF may be delivered. This is used bythe MME to connect with the SCEF. Therefore, the MME stores one SCEFreference ID. The SCEF stores one SCEF reference ID bound with severalSCS/AS reference IDs. Therefore, the MME knows one SCEF reference IDonly, and may perform binding of one SCEF reference ID only for one UEwhen establishing an SCEF data delivery connection between the UE andthe MME.

The SCEF data delivery establishment procedure between the UE and theMME is the same as that in the sixth-third embodiment.

A difference is to be able to include the following information in theuplink NAS transfer message when the UE sends MO data.

Connectivity type=To identify a message for transmitting data to theSCEF

Data payload=Data to be sent to a target SCS/AS, and identifierinformation for the target SCS/AS

The MME may identify the SCEF reference ID associated with the UEidentifier (IMSI), and delivers, to the corresponding SCEF, datareceived from the UE. The SCEF may look up data received from the MMEand thereby grasp identifier information for the target SCS/AS. Theidentifier information for the target SCS/AS may be expressed as anSCS/AS fully qualified domain name (FQDN), an SCS/AS ID, an IP Address,and the like.

The UE may acquire the identifier information for the target SCS/AS froma specific application, or utilize information configured in the UE.

Sixth-Sixth Embodiment

The sixth-sixth embodiment of the present invention relates to a messageconfiguration method when the UE desires to send data to the SCEF.

When the UE desires to send data to the SCEF, a message format complyingbetween the UE and the SCEF may be used. This may be referred to as asmall data transmission protocol.

This message format should include at least one of the followinginformation.

SCEF reference ID: To identify the connection between the MME and theSCEF, or to identify the connection between the SCEF and the SCS/AS.

SCS/AS ID: An identity for identifying the target SCS/AS at the SCEF.

SCS/AS reference ID: An identity for identifying the target SCS/AS atthe SCEF.

External ID: An identity for identifying the UE at the target SCS/AS, oran identity for identifying the UE at the SCEF.

In addition, a cause may be included. This indicates, when datatransmission fails, a reason for the failure and an entity from whichthe failure occurs. The UE, the MME, or the SCEF may receive this andrequest to reestablish the connection of the specific entity. Forexample, the connection between the UE and the MME may be reestablished,the connection between the MME and the SCEF may be reestablished, andthe identifiers for the connection between the UE and the SCEF may bereallocated and exchanged.

Seventh Embodiment

The seventh embodiment of the present invention relates to a bearermanagement method when a cellular IoT UE uses a telephone service, andto an apparatus for performing the method.

In this disclosure, an EPS refers to an evolved packet system or an LTEnetwork. The EPS is composed of evolved universal terrestrial radioaccess network (E-UTRAN) between the UE and the eNB, and an evolvedpacket core (EPC) which is a core network of the LTE system. The EPC iscomposed of an MME, a serving gateway (S-GW), a PDN gateway (P-GW), anda PCRF.

In this disclosure, CIoT represents an IoT service using a cellularnetwork. The cellular network refers to a mobile communication network,including 2G represented by GERAN, 3G represented by GPRS, and 4Grepresented by LTE. The CIoT service refers to a cellular service forsupporting an Internet of Things (IoT) device, and may refer to aservice for transmitting a small amount of data through the cellularnetwork. It may also include a machine type communication (MTC) service.The cellular network includes not only a radio access network but also acore network.

For the CIoT, the existing network apparatus may be changed. Forexample, there may be a CIoT-dedicated base station (eNB), and a CIoTfunction may be added to the existing base station (eNB). In the presentinvention, such base stations (eNBs) will be referred to as a CIoT RANfor convenience. However, the present invention is not limited to thisterm, and other terms having equivalent technical meanings may be used.Similarly, a core network of the cellular network may exist for theCIoT. In the present invention, a core network entity for the CIoT willbe referred to as a CIoT core network (CN) node. Although this iscurrently referred to as C-SGN in 3GPP, the present invention is notlimited to this term, and other terms having equivalent technicalmeaning may be used. The CIoT CN node refers to an entity including thefunctions of the MME and a serving gateway in the current LTE system andmay be an entity including the function of a PDN gateway. Thus, in thepresent invention, the C-SGN may refer to the MME.

The CIoT CN node not only performs the context management, mobilitymanagement, and signaling session management of the CIoT UE, but alsodelivers data of the UE to an application server or delivers datareceived from the application server to the UE. That is, the CIoT CNnode provides a gateway function to the CIoT UE, and may serve as agateway for receiving data from the CIoT RAN and routing it to theapplication server. If the CIoT CN node includes the PDN Gatewayfunction, the CIoT CN node may directly transfer user plane data to theapplication server.

The CIoT UE infrequently transmits and receives small data. Therefore,without establishing a user plane connection between the CIoT UE and theCIoT CN node, only a control plane connection may be established totransmit the user plane data therethrough. As a result, by omitting theuser plane connection establishment, a user plane encryption operation,or a control information signaling procedure for the user planeconnection establishment, the efficiency may be obtained at the radioresources and the network. This scheme will be referred to as a controlplane (CP) based solution for the sake of convenience.

Unlike the above, the CIoT UE may establish a user plane connection andperform a small data transmission. The CIoT UE establishes an RRCconnection with the CIoT RAN, and the CIoT RAN establishes a user planebearer connection with the C-SGN through signaling. The CIoT UEestablishes a data radio bearer (DRB) connection with the CIoT RAN, andthe CIoT RAN establishes a user plane bearer connection with the C-SGN.Therefore, data transmitted by the CIoT UE is transferred via the userplane as in a conventional transmission scheme of the LTE UE. Forconvenience, this will be referred to as a user plane (UP) basedsolution in this disclosure.

FIG. 17 is a diagram illustrating an MO-based bearer management methodin an embodiment of the present invention.

Referring to FIG. 17, a communication system of this embodiment mayinclude a UE 1705, an eNB 1710, a BSS/RNS 1715, an MME 1720, an MSC1725, an S-GW/P-GW 1730, and an SGSN 1735.

At operation 1751, the UE 1705 may send an extended service requestmessage to the MME 1720. At operation 1753, the MME may send an SGsservice request message to the MSC 1725.

At operation 1755, the MME 1715 may transmit an S1-AP UE contextmodification request message or an S1-AP initial UE context requestmessage to the eNB 1710.

At operation 1757, the eNB 1710 may transmit the S1-AP UE contextmodification response message or the S1-AP initial UE context responsemessage to the MME 1715.

At operation 1759, the eNB 1710 may acquire measurement information fromthe UE 1705.

At operation 1761, the eNB 1710 may transmit an NACC connection releasemessage or an RRC connection release message to the UE 1705.

At operation 1763, the eNB 1710 may transmit an S1-AP UE context releaserequest message to the BSS/RNS 1715.

At operation 1765, the MME 1720 may release UE context of the eNB 1710.At operation 1767, the UE 1705 moves to the target RAT and establishes aradio signaling connection.

If PS handover is supported, a handover procedure is performed insteadof the operations 1763 and 1765. Therefore, a packet switched (PS)service may be continuously used at the target RAT that uses circuitswitched (CS).

At operation 1769, the UE 1705 determines whether to suspend a bearer.

When the UE moves to the target RAT instead of LTE to use circuitswitched fall back (CSFB), the UE may temporarily suspend the bearer inpreparation for returning to the LTE network after using a telephoneservice. If the UE is using the CIoT service in LTE, the UE may have aCP-based data transmission bearer for transmitting data through thecontrol plane. In this case, since there is no user plane bearer amongthe UE, the eNB and the gateway, the bearer suspend procedure may not beperformed.

If the UE has at least one CP-based data transmission bearer and atleast one UP-based data transmission bearer, the UE may insert anidentifier of the UP-based data transmission bearer in a bearer suspendrequest message of operation 1771 in order to suspend only the UP-baseddata transmission bearer. Alternatively, even though the UE does notinsert the ID of the UP-based data transmission bearer, the SGSN 1735that receives this message may perform operation 1773 to suspend onlythe UP-based data transmission bearer.

At the operation 1773, the MME 1720 that receives the message may graspthe CP-based data transmission bearer and the UP-based data transmissionbearer which have been possessed by the UE 1705, determine to suspendonly the UP-based data transmission bearer, and exchange messages withthe S-GW/P-GW at operations 1777 and 1779.

If the UE has at least one CP-based data transmission bearer, the bearersuspend procedure may not be performed even though there is the UP-baseddata transmission bearer. As a result, all the UP-based datatransmission bearers are released, and only information about theCP-based data transmission bearer remains between the UE and the MMEwhen the UE completes a CS service and returns to the LTE network.Alternatively, even if the UE has only the CP-based data transmissionbearer, the bearer suspend procedure may be performed.

If the UE has used the CP-based data transmission bearer, the MME 1720confirms that the UE has used the CP-based data transmission bearer, andsends a suspend notification to the S-GW 1730 through the S11 interfaceat operation 1777 in order to suspend the CP-based data transmissionbearer. Passing through the S11 interface means the CP-based datatransmission bearer. The MME 1720 may insert an indication (i.e., EPSbearer ID, etc.) indicating the CIoT control plane optimization in thesuspend notification to be sent to the S-GW 1730. The S-GW 1730 thatreceives the suspend notification suspends the bearer for the CIoTcontrol plane optimization between the S-GW 1730 and the MME 1720.

Or, if the MME 1720 determines that the UE has only the CP-based datatransmission bearer, the MME 1720 may process the bearer in a suspendstate therein without requesting the bearer suspend to the S-GW 1730.When the UE returns to the MME 1720 again, the MME 1720 may activateagain and use the bearer context of the suspended bearer. Therefore, theMME 1720 does not interact with the S-GW 1730 in the suspend operationand the reactivation operation.

Or, if the UE has also the UP-based data transmission bearer, the MME1720 may suspend only a default bearer among UP-based data transmissionbearers. This may occur in parallel with the operation of suspending theCP-based data transmission bearer, or occur only for the UP-based datatransmission bearer without suspending the CP-based data transmissionbearer.

At operation 1781, the UE 1705 may transmit a CM service request messageto the MSC 1725. This message may include information indicating an MOcall by the CSFB.

At operation 1783, the UE 1705 may use a CS call. At operation 1785, theCS call may be terminated.

FIG. 18 is a diagram illustrating an MT-based bearer management methodin an embodiment of the present invention.

Referring to FIG. 18, a communication system of this embodiment mayinclude a UE 1805, an eNB 1810, a BSS/RNS 1815, an MME 1820, an MSC1825, an S-GW/P-GW 1830, and an SGSN 1835.

At operation 1851, the MSC 1825 receives an incoming voice call andsends a paging request message to the MME 1820. At operation 1853, theMME 1820 sends the paging request message to the eNB 1810. At operation1855, the eNB 1810 performs a paging operation for the UE 1805. The eNB1810 may send a paging message to the UE 1805.

At operation 1857, the UE 1805 may send an extended service requestmessage to the MME 1820 for MT CS fall back. At operation 1859, the MME1820 may send a SGs service request message to the MSC 1825, and informthe MSC 1825 that the UE 1805 is in a connected mode. Using this, theMSC 1825 may perform call forwarding to the UE 1805.

At operation 1861, the MME 1820 may send an S1-AP initial UE contextrequest message to the eNB 1810. This message may include a CS fall backindicator and an LAI. This message may instruct the UE 1805 to move touniversal terrestrial radio access network (UTRAN) or GERAN.

At operation 1863, the eNB 1810 may send the S1-AP initial UE contextresponse message to the MME 1820.

At operation 1865, the eNB 1810 may receive measurement information fromthe UE 1805 and may use the measurement information for determining atarget cell. The measurement information reception process may beomitted.

At operation 1867, the eNB 1810 may send an NACC connection releasemessage or an RRC connection release message to the UE 1805.

At operation 1869, the eNB 1810 may send an S1-AP UE context releaserequest message to the BSS/RNS 1815 and/or the MME 1820.

At operation 1871, the MME 1820 may release the UE context of the eNB1810. At operation 1873, the UE 1805 moves to the target RAT andestablishes a radio signaling connection.

If PS handover is supported, a handover procedure is performed insteadof the operations 1871 and 1873. Therefore, the PS service may becontinuously used at the target RAT that uses the CS.

When the UE moves to the target RAT instead of LTE in order to use theCSFB, the UE may temporarily suspend the bearer in preparation forreturning to the LTE network after using a telephone service. If the UEis using the CIoT service in LTE, the UE may have a CP-based datatransmission bearer for transmitting data through the control plane. Inthis case, since there is no user plane bearer among the UE, the eNB andthe gateway, the bearer suspend procedure may not be performed.

At operation 1875, the UE 1805 may determine whether to suspend thebearer temporarily. If the UE 1805 has at least one CP-based datatransmission bearer and at least one UP-based data transmission bearer,the UE 1805 may insert an identifier of the UP-based data transmissionbearer in a bearer suspend request message at operation 1877 in order tosuspend only the UP-based data transmission bearer. Alternatively, eventhough the UE 1805 does not insert the ID of the UP-based datatransmission bearer, the SGSN 1835 that receives this message mayperform operation 1879 to suspend only the UP-based data transmissionbearer. Alternatively, the MME 1820 that receives the suspend requestmessage of the operation 1879 may send a suspend response message to theSGSN. The MME 1820 may grasp the CP-based data transmission bearer andthe UP-based data transmission bearer which have been possessed by theUE 1805, determine to suspend only the UP-based data transmissionbearer, and exchange messages with the S-GW/P-GW 1830. The MME 1820 maysend a suspend notification message to the S-GW/P-GW 1830 at operation1883, and the 5-GW/P-GW 1830 may send a suspend acknowledge message tothe MME 1820 at operation 1885.

If the UE 1805 has at least one CP-based data transmission bearer, thebearer suspend procedure may not be performed even though there is theUP-based data transmission bearer. As a result, all the UP-based datatransmission bearers are released, and only information about theCP-based data transmission bearer remains between the UE 1805 and theMME 1820 when the UE completes a CS service and returns to the LTEnetwork.

Alternatively, even if the UE 1805 has only the CP-based datatransmission bearer, the bearer suspend procedure may be performed.

If the UE 1805 has used the CP-based data transmission bearer, the MME1820 confirms that the UE has used the CP-based data transmissionbearer, and sends a suspend notification to the S-GW through the S11interface at operation 1883 in order to suspend the CP-based datatransmission bearer. Passing through the S11 interface means theCP-based data transmission bearer. The MME 1820 may insert an indication(i.e., EPS bearer ID, etc.) indicating the CIoT control planeoptimization in the suspend notification to be sent to the S-GW 1830.The S-GW 1830 that receives the suspend notification suspends the bearerfor the CIoT control plane optimization between the S-GW 1830 and theMME 1820.

Or, if the MME 1820 determines that the UE 1805 has only the CP-baseddata transmission bearer, the MME 1820 may process the bearer in asuspend state therein without requesting the bearer suspend to the S-GW1830. When the UE 1805 returns to the MME 1820 again, the MME 1820 mayactivate again and use the bearer context of the suspended bearer.Therefore, the MME does not interact with the S-GW in the suspendoperation and the reactivation operation.

Or, if the UE 1805 has also the UP-based data transmission bearer, theMME 1820 may suspend only a default bearer among UP-based datatransmission bearers. This may occur in parallel with the operation ofsuspending the CP-based data transmission bearer, or occur only for theUP-based data transmission bearer without suspending the CP-based datatransmission bearer.

At operation 1887, the UE 1805 may send a paging response message to theMSC 1825.

At operation 1189, the UE 1805 may use a CS call. At operation 1891, theCS call may be terminated.

FIG. 19 is a diagram illustrating a procedure after a call is terminatedin an embodiment of the present invention.

Referring to FIG. 19, a communication system of this embodiment mayinclude a UE 1905, an eNB 1910, a BSS/RNS 1915, an MME 1920, an MSC1925, an S-GW/P-GW 1930, and an SGSN 1935.

At operation 1951 the UE 1905 is using a CS call, and at operation 1953the UE 1905 may terminate the CS call. When the CS call is terminated,the UE 1905 may access again E-UTRAN at operation 1955.

At operation 1957, the UE 1905 may send a tracking area update (TAU)request message to the MME 1920. When returning to the LTE network afterCSFB, the UE 1905 may select whether to use CIoT control planeoptimization, CIoT user plane optimization, or normal EPC. When sendingthe TAU request, the UE may insert an indication for the selection. Atoperation 1959, the MME 1920 may transmit a resume notification messageor a modify bearer request message to the P-GW/S-GW 1930.

The MME 1920 looks up an indication for a CIoT function included in theTAU request, and when the UE 1905 intends to use the CIoT control planeoptimization, the MME 1920 sends the modify bearer request includingrelated bearer context to the S-GW 1930. The bearer context of thismessage includes an address (e.g., TEID) of the S11-U interface. Thisaddress is an address of the S-GW 1930 used for the CP-based datatransmission bearer.

If the UE 1905 intends to use the CIoT control plane optimization, andif the UE 1905 does not have the UP-based data transmission bearersuspended to go to the CSFB, the UE 1905 may update the CP-based datatransmission bearer information without performing the modify bearerrequest to the S-GW 1930.

The MME 1920 may send the modify bearer request for both the UP-baseddata transmission bearer and the CP-based data transmission bearer whichare suspended by the UE. At this time, the bearer context of the modifybearer request message may include an S1-U interface address and anS11-U interface address. Based on the distinction between S1-U andS11-U, the S-GW 1930 may determine whether the bearer context is for theCP-based data transmission bearer or for the UP-based data transmissionbearer.

The message transmitted at the operation 1959 may be a resumenotification, and refers to a message that triggers an operation ofupdating the bearer connection information through the bearer context.

At operation 1961, the S-GW/P-GW 1930 may send a resume acknowledgemessage or a modify bearer response message to the MME 1920.

At operation 1963, the MME 1920 sends a TAU accept message to the UE1905, and may insert information about the updated, available bearercontext. For example, an EPS bearer ID and an identifier indicatingwhether the bearer is the CP-based data transmission bearer or theUP-based data transmission bearer may be inserted.

After completing TAU, the MME 1920 performs a release. At operation1965, the MME 1920 may send a UE context release command message to theeNB 1910. At operation 1967, the eNB 1910 may send an RRC releasemessage to the UE 1905. Thereafter, at operation 1969, the eNB 1910 maysend a UE context release complete message to the MME 1920.

FIG. 20 is a diagram illustrating an application server (AS) accordingto an embodiment of the present invention.

Referring to FIG. 20, the AS 2000 may include a transceiver 2010 fortransmitting and/or receiving signals and a controller 2030 forcontrolling the operation of the AS 2000. The controller 2030 mayinclude at least one processor. The controller 2030 may control theoperations of the AS and SCS/AS described above in the first to seventhembodiments. A detailed operation of the controller 2030 refers to theoperation of the AS in each embodiment.

FIG. 21 is a diagram illustrating an SCEF according to an embodiment ofthe present invention.

Referring to FIG. 21, the SCEF 2100 may include a transceiver 2110 fortransmitting and/or receiving signals and a controller 2130 forcontrolling the operation of the SCEF 2100. The controller 2130 mayinclude at least one processor. The controller 2130 may control theoperation of the SCEF described above in the first to seventhembodiments. A detailed operation of the controller 2130 refers to theoperation of the SCEF in each embodiment.

FIG. 22 is a diagram illustrating an HSS according to an embodiment ofthe present invention.

Referring to FIG. 22, the HSS 2200 may include a transceiver 2210 fortransmitting and/or receiving signals and a controller 2230 forcontrolling the operation of the HSS 2200. The controller 2230 mayinclude at least one processor. The controller 2230 may control theoperation of the HSS described above in the first to seventhembodiments. A detailed operation of the controller 2020 refers to theoperation of the HSS in each embodiment.

In embodiments of the present invention, each of a terminal (or UE), abase station (or eNB), an MME, and an SGSN may include a transceiver anda controller. Each of such entities may transmit and receive signalsthrough the transceiver thereof. The controller of each entity maycontrol the overall operation of each entity and may include at leastone processor. In addition, the controller of the terminal may controlthe operation of the terminal described above in the first to seventhembodiments of the present invention, and the controller of the basestation may control the operation of the base station described above inthe first to seventh embodiments of the present invention. Also, thecontroller of the MME may control the operation of the MME describedabove in the first to seventh embodiments of the present invention, andthe controller of the SGSN may control the operation of the SGSNdescribed above in the first to seventh embodiments of the presentinvention. A detailed operation of the controller for controlling eachentity refers to the operation of each entity in each embodiment.

It should be noted that the embodiments disclosed in this descriptionand drawings are only illustrative examples of the present invention andare not intended to limit the scope of the present invention. Therefore,the scope of the present invention should be construed as including allthe modifications or variations derived from the technical idea of thepresent invention in addition to the embodiments disclosed herein.

The invention claimed is:
 1. A method performed by an application server(AS), the method comprising: transmitting, to a service capabilityexposure function (SCEF), a monitoring request message including amonitoring duration, an identifier of a group including one or moreterminals, a time and a monitoring type associated with a monitoringevent; and receiving a monitoring indication message, transmitted fromthe SCEF based on an expiration of the time, including aggregated atleast one monitoring event report which has been detected for at leastone terminal among the one or more terminals, wherein the time is lessthan the monitoring duration.
 2. The method of claim 1, wherein the timeindicates time information for which the at least one monitoring eventreport is aggregated.
 3. An application server (AS) comprising: atransceiver; and a controller configured to: transmit, to a servicecapability exposure function (SCEF) via the transceiver, a monitoringrequest message including a monitoring duration, an identifier of agroup including one or more terminals, a time and a monitoring typeassociated with a monitoring event, and receive, from the SCEF based onan expiration of the time via the transceiver, a monitoring indicationmessage including aggregated at least one monitoring event report whichhas been detected for at least one terminal among the one or moreterminals, wherein the time is less than the monitoring duration.
 4. TheAS of claim 3, wherein the time indicates time information for which theat least one monitoring event report is aggregated.
 5. A methodperformed by a service capability exposure function (SCEF), the methodcomprising: receiving, from an application server (AS), a monitoringrequest message including a group identifier of a group including one ormore terminals, a time and a monitoring type associated with amonitoring event; transmitting, to a home subscriber server (HSS), amessage including the group identifier, the time and the monitoringtype; aggregating at least one monitoring event report received from amobility management entity (MME) wherein the at least one monitoringevent report which has been detected for at least one terminal among theone or more terminals; and transmitting, to the AS, a monitoringindication message including the aggregated at least one monitoringevent report based on an expiration of the time.
 6. The method of claim5, wherein the time indicates time information for which the at leastone monitoring event report is aggregated.
 7. The method of claim 5,wherein the at least one monitoring event report obtained until theexpiration of the time is accumulated for the monitoring indicationmessage.
 8. The method of claim 5, wherein the monitoring requestmessage includes a monitoring duration, and wherein the time is lessthan a monitoring duration.
 9. The method of claim 5, furthercomprising: receiving at least one monitoring event report that isaggregated at the HSS based on the time.
 10. A service capabilityexposure function (SCEF) comprising: a transceiver; and a controllerconfigured to: receive, from an application server (AS) via thetransceiver, a monitoring request message including a group identifierof a group including one or more terminals, a time and a monitoring typeassociated with a monitoring event, transmit, to a home subscriberserver (HSS) via the transceiver, a message including the groupidentifier, the time and the monitoring type, aggregate at least onemonitoring event report received from a mobility management entity (MME)wherein the at least one monitoring event report which has been detectedfor at least one terminal among the one or more terminals, and transmit,to the AS via the transceiver, a monitoring indication message includingthe aggregated at least one monitoring event report based on anexpiration of the time.
 11. The SCEF of claim 10, wherein the timeindicates time information for which the at least one monitoring eventreport is aggregated.
 12. The SCEF of claim 10, wherein the at least onemonitoring event report obtained until the expiration of the time isaccumulated for the monitoring indication message.
 13. The SCEF of claim10, wherein the monitoring request message includes a monitoringduration, and wherein the time is less than a monitoring duration. 14.The SCEF of claim 10, wherein the controller is further configured toreceive at least one monitoring event report that is aggregated at theHSS.
 15. A method performed by a home subscriber server (HSS), themethod comprising: receiving, from a service capability exposurefunction (SCEF), a monitoring request message including a monitoringduration, a group identifier of a group including one or more terminals,a time and a monitoring type associated with a monitoring event;accumulating at least one monitoring event report which has beendetected for at least one terminal among the one or more terminals; andtransmitting, to the SCEF, the at least one monitoring event reportbased on an expiration of the time, wherein the time is less than themonitoring duration.
 16. A home subscriber server (HSS) comprising: atransceiver; and a controller configured to: receive, from a servicecapability exposure function (SCEF) via the transceiver, a monitoringrequest message including a monitoring duration, a group identifier of agroup including one or more terminals, a time and a monitoring typeassociated with a monitoring event report, accumulate at least onemonitoring event report which has been detected for at least oneterminal among the one or more terminals included in the group based onthe time, and transmit, to the SCEF via the transceiver, the at leastone monitoring event report based on an expiration of the time, whereinthe time is less than the monitoring duration.